Installed and tested.

@donald why not merged then?

Tabs are evil. Please don't use them. There is no standard concerning size, so using them rips intended formatting.

issue: bash broke <<- redirection operator. leading tabs get deleted.

next time I'll use sed to get rid of the spaces in the output if that is a deep concern.

" bash broke <<- redirection operator" is a funny way to say that you wrongly used space instead of tab. But I didn't catch it either.
Anyway, its no real problem, just four spaces at the beginning of the lines of the profile scripts in the llvm packages. We can live with that.

Probably caused by a smart editor converting between tabs and spaces on its own.

It makes sense to avoid this danger in the future by not indenting the HERE docs at all.

why not just use sed?

sed 's/^    //' > FILENAME <<EOF
    FILE
    CONTENT
        WANTED INDENTED
EOF

> cat FILENAME
FILE
CONTENT
    WANTED INDENTED

Same problem, if editor replaces a string of spaces by tabs on the "WANTED INDENTED" line.
How about

sed 's/\s*|//' >test.txt <<EOF
    |FILE
    |CONTENT
    |   WANTED INDENTED
EOF

Edit: Changed <<-EOF into <<EOF

No idea, why there were so many misunderstanding, and why it blew up. I just commented on a minor detail, so next time it can be avoided. Here-documents are pretty handy, and shorter than the sed hacks.

I agree on the style provided by Donald.

The problem is that there is no reason to use tabs and many against it. Furthermore, shorter but more error-prone in real life. Eleven characters can solve all the issues and being easy to read and understand. Also it's not an overall commitment, so feel free to use tabs in your scripts. You correctly mentioned my non-awareness of the <<- docs but I dislike the recommendation of that and therefore we discussed an alternative.